Changes

Note
Your Auth0 tenant must have this feature enabled to use this.

This PR adds support for authorizing using an organization name. This enhances the existing support for authorizing using an organization ID. Example usage follows:

✨ (New) Authorization using an organization name:

new Auth0(
  new SdkConfiguration(
    organization: ['example-org-name'],
  )
);

(Existing) support for authorization using an organization ID:

new Auth0(
  new SdkConfiguration(
    organization: ['org_123456'],
  )
);

(Updated) The SDK treats the organization parameter as an allowlist for applications that need to work with multiple organizations. It now accepts organization names, as well as existing support for IDs.

$sdk = new Auth0(
  new SdkConfiguration(
    organization: ['org_123456', 'example-org-name', 'another-org-name'],
  )
);

(Existing) When redirecting for authorization, the organization allowlist's first value is used by default. This behavior can be overridden using method parameters:

// Redirects to /authorize?organization=org_123456&...
header('Location: ' . $sdk->login());

// Redirects to /authorize?organization=org_000000&...
header('Location: ' . $sdk->login(params: ['organization': 'org_000000'));

// Redirects to /authorize?organization=example-org-name&...
header('Location: ' . $sdk->login(params: ['organization': 'example-org-name'));

// Redirects to /authorize?...
header('Location: ' . $sdk->login(params: ['organization': null));

References

Please review the internal Jira ticket SDK-4393 for further information.

Testing

• Tests have been updated to support the new functionality and maintain 100% coverage.
• Run composer test from a clone of the branch to test locally.
• Review the CI test results on the PR otherwise.

Contributor Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 code of conduct